home *** CD-ROM | disk | FTP | other *** search
- Path: engnews1.Eng.Sun.COM!usenet
- From: thp@cs.ucr.edu (Tom Payne)
- Newsgroups: comp.std.c++
- Subject: Re: Referencing pointers after delete
- Date: 25 Mar 1996 17:27:32 GMT
- Organization: University of California, Riverside
- Approved: clamage@eng.sun.com (comp.std.c++)
- Message-ID: <4j6k0r$hev@galaxy.ucr.edu>
- References: <4iushh$q3@galaxy.ucr.edu> <4ivdsv$p3p@engnews1.Eng.Sun.COM>
- NNTP-Posting-Host: taumet.eng.sun.com
- X-Nntp-Posting-Host: corvette.ucr.edu
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
- Content-Length: 1203
- X-Lines: 26
-
- Steve Clamage (clamage@Eng.Sun.COM) wrote:
- : In article q3@galaxy.ucr.edu, thp@cs.ucr.edu (Tom Payne) writes:
- [...]
- : >I don't mean to imply that one can portably detect *all* invalid
- : >pointers, but with help from the compiler software-based solutions
- : >can give coverage that is as complete as those based on hardware.
- : >In either case, it is not particularly helpful that the behavior
- : >becomes undefined the moment an invalid value is detected.
- [...]
- : Pointer validation isn't going to be portable, as I pointed out before.
-
- The issue is not so much the portability of the checking but the
- portability of programs that want to invoke it without voiding their
- defined-behavior contract with the underlying implemention.
-
- : I don't see any advantage in trying to restrict the kind or form of checking
- : that systems are allowed to implement. I would applaud a hardware-based
- : mechanism, and I would resent a programming language standard that made
- : it non-conforming.
-
- The issue is not the form of the checking but the response to it. The
- standard response to a hardware-detected fault is to invoke a signal
- handler, which is (or should be) completely conforming.
-
- Tom Payne (thp@cs.ucr.edu)
-
-
-
- [ comp.std.c++ is moderated. To submit articles: try just posting with ]
- [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
- [ FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html ]
- [ Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
- [ Comments? mailto:std-c++-request@ncar.ucar.edu ]
-